Systems and methods for data type identification and adjustment

ABSTRACT

A system includes an operating system executed by a processor and memory. A data type identifier changing application is executed by the operating system and is configured to display a table including data entries that are arranged in rows and columns and that include data type identifiers. The data type identifier changing application is configured to generate a list including two or more of the data type identifiers corresponding to rows in a selected column. The data type identifier changing application is configured to change one of the data type identifiers in the list corresponding to a plurality of rows in the selected column to one of another one of the data type identifiers in the list or a data type identifier that is not in the list.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. application Ser. No. 15/270,396, filed on Sep. 20, 20216, the entirety of which is incorporated herein by reference.

FIELD

The present disclosure relates to systems and methods for changing data type identifiers in columns of tables.

BACKGROUND

The background description provided herein is for the purpose of generally presenting the context of the disclosure. Work of the presently named inventors, to the extent the work is described in this background section, as well as aspects of the description that may not otherwise qualify as prior art at the time of filing, are neither expressly nor impliedly admitted as prior art against the present disclosure.

Data wrangling typically involves extracting raw data from a data source and sorting, transforming and/or formatting the raw data. The data may be loaded into one or more tables. Each of the tables may be used to store related types of data (such as employee data, customer addresses, sales data, etc.) using a fixed number of columns and a variable number of rows. Data wrangling may also involve normalization, which is the process of organizing the columns and tables of a relational database to reduce data redundancy and improve data integrity.

Each column in a table usually includes related types of data. Examples of related types of data that may appear in the columns of a sales-related table include customer name, product identification, quantity sold, sales price, etc. Users may assign a data type identifier to the data in each row of the column. The data type identifiers for each entry in the table may be stored as metadata associated with the data entries in each row/column location. Examples of data type identifiers include text, numerical data type identifiers (such as integer or more complex number formats), logical data type identifiers (such as Boolean), date and time data type identifiers, etc. Data type identifiers may also determine the types of operations that can be performed on the entry in a spreadsheet or database and help to determine the meaning of an entry (for example, a number in a row may be used to represent text, an amount, or a date depending on the data type identifier).

Data type mismatches occur when a column of a table includes one or more rows having different data type identifiers. In some situations, data wranglers may have various different types of data within a single column because users incorrectly imputed that data. A data quality bar is the primary mechanism for knowing whether the data type identifier is mismatched (in other words, by inference when some entries are valid, invalid, or unknown).

SUMMARY

A system includes an operating system executed by a processor and memory. A data type identifier changing application is executed by the operating system and is configured to a) display a table including data entries that are arranged in rows and columns and that include data type identifiers; b) generate a list including two or more of the data type identifiers corresponding to rows in a selected column; and c) change one of the data type identifiers in the list corresponding to a plurality of rows in the selected column to one of: another one of the data type identifiers in the list; or a data type identifier that is not in the list.

In other features, the data type identifier changing application generates row counts corresponding to a number of rows in the selected column having a corresponding one of the data type identifiers and displays the row counts in the list. The data type identifier includes data entities. At least one of the data entities is selected from a group consisting of an address, a social security number, a phone number, and a zip code.

In other features, the data type identifier changing application selectively repeats a), b) and c) until only one of the data type identifiers is associated with the selected column. The data type identifier changing application is configured as an add-in application to an application selected from a group consisting of a database application, a spreadsheet application, and a data wrangling application. The data type identifier changing application selectively displays sample data entries in rows of one of the data type identifiers in the list. The data type identifier changing application selectively displays a preview of changed data entries in rows corresponding to one of the data type identifiers in the list if the change is made.

In other features, the list is displayed in a dialog box including a plurality of command buttons corresponding to the data type identifiers. Each of the plurality of command buttons includes a text descriptor for a corresponding one of the data type identifiers. The text descriptor further includes a count of rows for the corresponding one of the data type identifiers.

A non-transitory, tangible computer-readable medium stores instructions for changing data type identifiers. The non-transitory, tangible computer-readable medium includes instructions for a) displaying a table including data entries that are arranged in rows and columns and that include data type identifiers; b) generating a list including two or more of the data type identifiers corresponding to rows in a selected column; and c) changing one of the data type identifiers in the list corresponding to a plurality of rows in the selected column to one of: another one of the data type identifiers in the list; or a data type identifier that is not in the list.

In other features, non-transitory, tangible computer-readable medium stores instructions for generating row counts corresponding to a number of rows in the selected column having a corresponding one of the data type identifiers; and displaying the row counts in the list.

In other features, the data type identifier includes data entities. At least one of the data entities is selected from a group consisting of an address, a social security number, a phone number, and a zip code.

In other features, non-transitory, tangible computer-readable medium stores instructions for allowing a user to repeat a), b) and c) until only one of the data type identifiers is associated with the selected column.

In other features, non-transitory, tangible computer-readable medium stores instructions for displaying the list of the data type identifiers in a dialog box including a plurality of command buttons corresponding to the data type identifiers in the list; generating text descriptors for each corresponding one of the data type identifiers in the list; and generating a count of rows for the corresponding one of the data type identifiers and displaying the count in the text descriptors for each corresponding one of the data type identifiers.

In other features, non-transitory, tangible computer-readable medium stores instructions for selectively displaying sample data entries in rows of one of the data type identifiers in the list.

In other features, non-transitory, tangible computer-readable medium stores instructions for selectively displaying a preview of changed data entries in rows corresponding to one of the data type identifiers in the list if the change is made.

A system comprises a processor and memory. An operating system is executed by the processor and memory. A data type identifier changing application is executed by the operating system and is configured to: a) display a table including data entries that are arranged in rows and columns and that include data type identifiers; b) generate a list including two or more of the data type identifiers corresponding to rows in a selected column; c) generate row counts corresponding to a number of rows in the selected column having a corresponding one of the data type identifiers and display the row counts along with the list of the data type identifiers; d) change one of the data type identifiers in the list corresponding to a plurality of rows in the selected column to one of another one of the data type identifiers in the list or a data type identifier that is not in the list; and e) selectively repeat a), b), c) and d) until only one of the data type identifiers is associated with the selected column.

In other features, the data type identifier includes data entities. At least one of the data entities is selected from a group consisting of an address, a social security number, a phone number, and a zip code. The data type identifier changing application is configured as an add-in application to an application selected from a group consisting of a database application, a spreadsheet application, and a data wrangling application.

Further areas of applicability of the present disclosure will become apparent from the detailed description, the claims and the drawings. The detailed description and specific examples are intended for purposes of illustration only and are not intended to limit the scope of the disclosure.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a functional block diagram showing a computer including a data type identifier correcting application according to the present disclosure.

FIGS. 2-3 are flowcharts illustrating examples of a method for correcting data type identifiers according to the present disclosure.

FIGS. 4-9 are screen shots illustrating example dialog boxes for changing the data type identifier of a column of a table.

FIGS. 10-11 are screen shots illustrating example dialog boxes for changing the data type identifier of a column of a table to a data type identifier that is not associated with any data entries in rows of a selected column.

FIGS. 12-13 are screen shots illustrating example dialog boxes for previewing data entries in rows of a selected column that are to be changed as if the change was made.

FIGS. 14-15 are screen shots illustrating example dialog boxes for showing a sample of data entries in rows of a selected column having a selected data type identifier.

In the drawings, reference numbers may be reused to identify similar and/or identical elements.

DESCRIPTION

The present disclosure relates to systems and methods for changing the data type identifier of groups of rows in a column of a table. The rows with the data type identifier that is to be changed do not need to be located in consecutive rows in the selected column. As used herein, the term data type identifier refers to traditional data type identifiers described above and/or data entities such as addresses, social security numbers, phone numbers, zip codes, etc. that have hybrid data formats or special data formats.

More particularly, the systems and methods described herein allow a user to select a column of a table and generate summary data to allow the user to understand the different data type identifiers assigned to rows within the selected column. In some examples, the summary also includes the number of rows in the selected column having the corresponding data type identifier. The systems and methods provide a user interface to allow the user to change the data type identifier of a group of rows in the selected column to a different data type identifier. As a result, data type mismatch in a column can be corrected.

Referring now to FIG. 1, a computer 10 includes a processor 14, one or more input devices 16 (such as a keyboard, mouse, touchscreen, etc.) and memory 20. The memory 20 stores an operating system 24 and a data type identifier correcting application 28. The data type identifier correcting application 28 can be implemented as a stand-alone application or as an add-in application 28′ to a database application 29-1, a spreadsheet application 29-2, a data wrangling application 29-3, or other application that accesses data in the tables.

The computer 10 further includes a display subsystem 34 including a display 36 and bulk storage 40. In some examples, the bulk storage 40 includes nonvolatile memory such as solid-state memory or a hard disk drive that may be used to store tables that are accessed by the data type identifier correcting application 28. In some examples, the tables are associated with a database 44. The computer 10 may further include a network interface 46 such as a wired or wireless interface that communicates with a distributed communications system 50 such as the Internet. The computer 10 may access data (such as tables or a remote database 64) associated with a cloud services provider 60 or data (such as tables or a remote database 58) associated with a remote server 54.

Referring now to FIG. 2, a method 100 for operating the data type identifier correcting application 28 is shown. At 110, the user opens a table, selects one of the columns of the table and requests information relating to the data type identifiers in the column. In some examples, the user accesses menus or right-clicks on the column using the pointing device, although other selection methods may be used. A dialog box is presented to allow selection of one or more menu items, although other types of user interfaces may be used. At least one of the menu items includes changing data type identifiers for the selected column.

At 120, the data type identifier correcting application 28 displays a dialog box or other user interface with M data type identifiers appearing in the selected column and the number (or percentage) of rows in the selected column corresponding to each of the M data type identifiers, where M is an integer greater than one. At 130, the data type identifier correcting application 28 determines whether the user selects one of the M data type identifiers in the dialog box. If 130 is false, the method continues at 135 and determines whether the user has closed the dialog box. If 135 is true, the method returns to 110. If 135 is false, the method returns to 130.

When 130 is true, the method 100 continues at 140 and displays a dialog box with the remaining (M−1) data type identifiers in the selected column and an optional other data type. At 145, the method determines whether the user selects one of the remaining (M−1) data type identifiers or other data type. Selecting one of the remaining (M−1) data type identifiers can be used to initiate the change or a confirmation dialog box may be used before the change is completed.

If 145 is false, the method determines whether the user closes the dialog box at 150. If 150 is true, the method returns to 110. If 150 is false, the method returns to 145. When 145 is true, the method continues at 154 and determines whether the user selected the other data type. If 154 is false, the method changes the data type identifier of row data in the selected column having the selected one of the M data type identifiers to the selected one of the M−1 data type identifiers.

If 154 is true, the method displays a dialog box with a list of other data types at 156. For example, the list includes other data type identifiers that are available but not already represented in the rows of the selected column. Examples include traditional data type identifiers described above and/or data entities such as addresses, social security numbers, phone numbers, zip codes, etc. that have hybrid data formats or special data formats.

At 160, the method determines whether the user selects one of the other data types in the list. If 160 is false, the method determines whether the user closes the dialog box. If 164 is false, the method returns to 160. If 164 is true, the method continues at 145, 130 or 110. If 160 is true, the method changes the data type identifier of row data in the selected column having the selected one of the M data type identifiers to the selected one of the other data type identifiers.

As can be appreciated, the method 100 can be stopped or repeated until there is only a single data type identifier remaining in the selected column.

Referring now to FIG. 3, a method 200 for optionally providing additional functionality depending upon the outcome of the data type identifier change request in FIG. 2 is shown. At 220, the method determines whether there will be invalid data in one or more rows of the selected column if the requested data type identifier change is made. If 220 is true, the method 200 opens a dialog box with a notification message to inform the user and requests confirmation at 222. At 230, the method determines whether the user confirms. If 230 is true, the method continues with 240. If 230 is false, the data type identifier change is not performed at 234.

When 220 is false or 230 is true, the method 200 continues at 240 and determines whether the requested data type identifier change would cause invalid data in other columns (other than the currently selected column). If 240 is true, the method 200 opens a dialog box with a notification message at 244 and requests confirmation of the data type identifier change. At 248, if the user does not confirm, the data type identifier change is not made and the method continues at 234. If 240 is false or 248 is true, the method continues with 250. At 250, the method 200 changes the data type identifier of row data in the selected column having the selected one of the M data type identifiers to the selected one of the (M−1) data type identifiers or the selected one of the other data type identifiers.

Referring now to FIGS. 4-9, an example of a user interface for changing the data type identifier of a column is shown. In FIG. 4, when a user selects a column 300 of a table 310, a dialog box 320 or other user interface is generated. The dialog box 320 includes one or more selectable command buttons 324.

In FIG. 5, if the user selects one of the command buttons 324 of the dialog box 320, a dialog box 340 is presented and includes data type identifiers that are found in the selected column. In this example, there are 3 different data type identifiers including string, integer and date/time. The dialog box 340 includes command buttons 342-1, 342-2 and 342-3 with data type identifier descriptors and a count corresponding to the total number of row occurrences in the selected column for the corresponding data type identifier. In this example, there are 121 rows with the string data type identifier, 500 rows with the integer data type identifier and 23 rows with the date/time data type identifier. Providing the number of row occurrences helps the data wrangler decide whether or not to make a data type identifier change and/or to troubleshoot data type mismatch in the column.

In FIGS. 6-7, when a user positions a cursor over or otherwise selects the command button 342-1, a dialog box 355 or other user interface is presented that includes command buttons 346-1 and 346-2 corresponding to the remaining data type identifiers in the selected column and an optional other command button 346-X. In this example, the user selects a change from the string data type identifier to the integer data type identifier using the command button 346-1.

In FIG. 7, the dialog box 340 is updated and now includes the remaining data type identifiers after the data type identifier change was made. In this example, the string data type identifier no longer exists and the integer data type identifier is increased by the number of rows that were changed from the string data type identifier to the integer data type identifier. In this example, the integer data type identifier now corresponds to 621 rows of the column as shown in command button 342-4.

In FIGS. 8-9, the process can be repeated to make additional datatype identifier changes. A user can position the cursor or otherwise select the command button 342-3. A dialog box 350 is generated and includes the remaining data type identifiers in other rows and the optional other command button 346-X. The user selects a change to the integer data type identifier using the command button 350.

In FIG. 9, the dialog box 340 is updated and displays a command button 342-5 with a descriptor displaying the additional rows that now have the integer data type identifier. In this example, the 23 rows with the date/time data type identifier are now added to the rows with the integer data type identifier. As can be appreciated, the user can select the command button 342-5 and a dialog box (not shown) with the other command button 346-X can be presented to allow changes to a selected other data type identifier.

In FIGS. 10-11, the data type identifiers can be changed to a data type identifier (in FIG. 10) that is not in the list using the command button 346-X. When the command button 346-X is selected, a dialog box 400 is displayed and includes a list of other data type identifiers that can be selected. Each item in the list may correspond to a command button. Alternately, a drop-down box or other selection process may be used.

In the example in FIG. 11, the user selects a float data type identifier and the data entries corresponding to the string data type identifier are changed to the float data type 342-5. The process can be repeated for other data type identifiers such as the integer data type identifier 342-4 in FIG. 11.

Referring now to FIGS. 12-13, data entries in rows corresponding to a data type identifier that the user intends to change can be previewed. When a user clicks on one of the command buttons 346-1, 346-2 and 346-X, the user can select either a preview command button 410 or a change command button 420. If the preview button 420 is selected, a display box 430 in FIG. 13 is presented that shows a preview of some or all of the data entries in rows as if the change was made. If the user decides that the correct result occurred, the change can be made.

Referring now to FIGS. 14-15, data entries in rows corresponding to a data type identifier can be sampled to see what the data entries look like. When a user clicks on one of the command buttons 342-1, 342-2 and 342-3 to change the data type identifier, the user can select a command button 346-S to generate a display box with samples of data entries in rows corresponding to the selected data type identifier in the list. If the sample command button 346-S is selected, a display box 450 in FIG. 15 is presented that shows a sample of some or all of the data entries in rows corresponding to the data entries in rows corresponding to the selected data type identifier in the list.

The foregoing description is merely illustrative in nature and is in no way intended to limit the disclosure, its application, or uses. The broad teachings of the disclosure can be implemented in a variety of forms. Therefore, while this disclosure includes particular examples, the true scope of the disclosure should not be so limited since other modifications will become apparent upon a study of the drawings, the specification, and the following claims. It should be understood that one or more steps within a method may be executed in different order (or concurrently) without altering the principles of the present disclosure. Further, although each of the embodiments is described above as having certain features, any one or more of those features described with respect to any embodiment of the disclosure can be implemented in and/or combined with features of any of the other embodiments, even if that combination is not explicitly described. In other words, the described embodiments are not mutually exclusive, and permutations of one or more embodiments with one another remain within the scope of this disclosure.

Spatial and functional relationships between elements (for example, between modules, circuit elements, semiconductor layers, etc.) are described using various terms, including “connected,” “engaged,” “coupled,” “adjacent,” “next to,” “on top of,” “above,” “below,” and “disposed.” Unless explicitly described as being “direct,” when a relationship between first and second elements is described in the above disclosure, that relationship can be a direct relationship where no other intervening elements are present between the first and second elements, but can also be an indirect relationship where one or more intervening elements are present (either spatially or functionally) between the first and second elements. As used herein, the phrase at least one of A, B, and C should be construed to mean a logical (A OR B OR C), using a non-exclusive logical OR, and should not be construed to mean “at least one of A, at least one of B, and at least one of C.”

In the figures, the direction of an arrow, as indicated by the arrowhead, generally demonstrates the flow of information (such as data or instructions) that is of interest to the illustration. For example, when element A and element B exchange a variety of information but information transmitted from element A to element B is relevant to the illustration, the arrow may point from element A to element B. This unidirectional arrow does not imply that no other information is transmitted from element B to element A. Further, for information sent from element A to element B, element B may send requests for, or receipt acknowledgements of, the information to element A.

In this application, including the definitions below, the term “module” or the term “controller” may be replaced with the term “circuit.” The term “module” may refer to, be part of, or include: an Application Specific Integrated Circuit (ASIC); a digital, analog, or mixed analog/digital discrete circuit; a digital, analog, or mixed analog/digital integrated circuit; a combinational logic circuit; a field programmable gate array (FPGA); a processor circuit (shared, dedicated, or group) that executes code; a memory circuit (shared, dedicated, or group) that stores code executed by the processor circuit; other suitable hardware components that provide the described functionality; or a combination of some or all of the above, such as in a system-on-chip.

The module may include one or more interface circuits. In some examples, the interface circuits may include wired or wireless interfaces that are connected to a local area network (LAN), the Internet, a wide area network (WAN), or combinations thereof. The functionality of any given module of the present disclosure may be distributed among multiple modules that are connected via interface circuits. For example, multiple modules may allow load balancing. In a further example, a server (also known as remote, or cloud) module may accomplish some functionality on behalf of a client module.

The term code, as used above, may include software, firmware, and/or microcode, and may refer to programs, routines, functions, classes, data structures, and/or objects. The term shared processor circuit encompasses a single processor circuit that executes some or all code from multiple modules. The term group processor circuit encompasses a processor circuit that, in combination with additional processor circuits, executes some or all code from one or more modules. References to multiple processor circuits encompass multiple processor circuits on discrete dies, multiple processor circuits on a single die, multiple cores of a single processor circuit, multiple threads of a single processor circuit, or a combination of the above. The term shared memory circuit encompasses a single memory circuit that stores some or all code from multiple modules. The term group memory circuit encompasses a memory circuit that, in combination with additional memories, stores some or all code from one or more modules.

The term memory circuit is a subset of the term computer-readable medium. The term computer-readable medium, as used herein, does not encompass transitory electrical or electromagnetic signals propagating through a medium (such as on a carrier wave); the term computer-readable medium may therefore be considered tangible and non-transitory. Non-limiting examples of a non-transitory, tangible computer-readable medium are nonvolatile memory circuits (such as a flash memory circuit, an erasable programmable read-only memory circuit, or a mask read-only memory circuit), volatile memory circuits (such as a static random access memory circuit or a dynamic random access memory circuit), magnetic storage media (such as an analog or digital magnetic tape or a hard disk drive), and optical storage media (such as a CD, a DVD, or a Blu-ray Disc).

In this application, apparatus elements described as having particular attributes or performing particular operations are specifically configured to have those particular attributes and perform those particular operations. Specifically, a description of an element to perform an action means that the element is configured to perform the action. The configuration of an element may include programming of the element, such as by encoding instructions on a non-transitory, tangible computer-readable medium associated with the element.

The apparatuses and methods described in this application may be partially or fully implemented by a special purpose computer created by configuring a general purpose computer to execute one or more particular functions embodied in computer programs. The functional blocks, flowchart components, and other elements described above serve as software specifications, which can be translated into the computer programs by the routine work of a skilled technician or programmer.

The computer programs include processor-executable instructions that are stored on at least one non-transitory, tangible computer-readable medium. The computer programs may also include or rely on stored data. The computer programs may encompass a basic input/output system (BIOS) that interacts with hardware of the special purpose computer, device drivers that interact with particular devices of the special purpose computer, one or more operating systems, user applications, background services, background applications, etc.

The computer programs may include: (i) descriptive text to be parsed, such as JavaScript Object Notation (JSON), hypertext markup language (HTML) or extensible markup language (XML), (ii) assembly code, (iii) object code generated from source code by a compiler, (iv) source code for execution by an interpreter, (v) source code for compilation and execution by a just-in-time compiler, etc. As examples only, source code may be written using syntax from languages including C, C++, C #, Objective C, Haskell, Go, SQL, R, Lisp, Java®, Fortran, Perl, Pascal, Curl, OCaml, Javascript®, HTML5, Ada, ASP (active server pages), PHP, Scala, Eiffel, Smalltalk, Erlang, Ruby, Flash®, Visual Basic®, Lua, and Python®.

None of the elements recited in the claims are intended to be a means-plus-function element within the meaning of 35 U.S.C. § 112(f) unless an element is expressly recited using the phrase “means for,” or in the case of a method claim using the phrases “operation for” or “step for.” 

1-20. (canceled)
 21. A system comprising: a processor and memory; an operating system executed by the processor and memory; a data type identifier changing application that is executed by the operating system and that is configured to: identify a dataset including a plurality of data entries, each data entry from the plurality of data entries having a data type identifier indicating a type of data for a value in the corresponding data entry; determine mismatched data type identifiers within the dataset based on a first subset of data entries from the dataset being associated with a first data type and a second subset of data entries from the dataset being associated with a second data type, wherein determining the mismatched data type identifiers is based on the first data type being incompatible with performing an operation that calls for the second data type; and based on determining the mismatched data type identifiers between the first subset of data entries and the second subset of data entries, cause each value from the first subset of data entries to be reassigned to the second data type.
 22. The system of claim 21, wherein the dataset includes a relational database of data including a table of data entries, the table of data entries being organized in a plurality of columns and a plurality of rows.
 23. The system of claim 22, wherein the plurality of data entries includes a selected column or row of data entries within the table of data entries, and wherein the first subset of data entries and the second subset of data entries are interspersed throughout the selected column or row of data entries.
 24. The system of claim 21, wherein the data type identifier for each data entry includes data type metadata associated with a respective data entry indicating the type of data, and wherein causing each value from the first subset of data entries to be reassigned to the second data type includes modifying data type metadata associated with the first subset of entries to match data type metadata for the second subset of entries.
 25. The system of claim 21, wherein where determining the mismatched data type identifiers includes: detecting a selection of a grouping of data entries from the dataset; identifying the first subset of data entries based on data entries from the selected grouping of data entries being associated with a first data type; and identifying the second subset of data entries based on data entries from the selected grouping of data entries being associated with a second data type being different from the first data type and being incompatible with performing the operation that calls for the second data type.
 26. The system of claim 21, wherein at least one data type identifier from the two or more data type identifiers include data entities selected from one or more of an address, a social security number, a phone number, or a zip code.
 27. The system of claim 21, wherein the data type identifier changing application is further configured to: determine additional mismatched data type identifiers within the dataset based on a third subset of data entries from the dataset being associated with a third data type from the reassigned second data type, wherein determining the additional mismatched data type identifiers is based on the third data type being incompatible with performing the operation that calls for the reassigned second data type; and based on determining the additional mismatched data type identifiers, cause each value from the third subset of data entries to be reassigned to the second data type.
 28. The system of claim 21, wherein the data type identifier changing application is configured as an add-in application to an application selected from one or more of a database application, a spreadsheet application, or a data wrangling application.
 29. The system of claim 21, wherein causing each value from the first subset of data entries to be reassigned to the second data type includes: determining whether reassigning the first data type identifier to the second data type identifier for any of the first subset of data entries would cause invalid data in other entries from the dataset; and reassigning the first subset of data entries to the second data type is based on determining that reassigning the first data type identifier to the second data type identifier would not cause invalid data in other entries from the dataset.
 30. A method, comprising: identifying a dataset including a plurality of data entries, each data entry from the plurality of data entries having a data type identifier indicating a type of data for a value in the corresponding data entry; determining mismatched data type identifiers within the dataset based on a first subset of data entries from the dataset being associated with a first data type and a second subset of data entries from the dataset being associated with a second data type, wherein determining the mismatched data type identifiers is based on the first data type being incompatible with performing an operation that calls for the second data type; and based on determining the mismatched data type identifiers between the first subset of data entries and the second subset of data entries, causing each value from the first subset of data entries to be reassigned to the second data type.
 31. The method of claim 30, wherein the dataset includes a relational database of data including a table of data entries, the table of data entries being organized in a plurality of columns and a plurality of rows.
 32. The method of claim 31, wherein the plurality of data entries includes a selected column or row of data entries within the table of data entries, and wherein the first subset of data entries and the second subset of data entries are interspersed throughout the selected column or row of data entries.
 33. The method of claim 30, wherein the data type identifier for each data entry includes data type metadata associated with a respective data entry indicating the type of data, and wherein causing each value from the first subset of data entries to be reassigned to the second data type includes modifying data type metadata associated with the first subset of entries to match data type metadata for the second subset of entries.
 34. The method of claim 30, wherein where determining the mismatched data type identifiers includes: detecting a selection of a grouping of data entries from the dataset; identifying the first subset of data entries based on data entries from the selected grouping of data entries being associated with a first data type; and identifying the second subset of data entries based on data entries from the selected grouping of data entries being associated with a second data type being different from the first data type and being incompatible with performing the operation that calls for the second data type.
 35. The method of claim 30, wherein at least one data type identifier from the two or more data type identifiers include data entities selected from one or more of an address, a social security number, a phone number, or a zip code.
 36. The method of claim 30, wherein the data type identifier changing application is further configured to: determine additional mismatched data type identifiers within the dataset based on a third subset of data entries from the dataset being associated with a third data type from the reassigned second data type, wherein determining the additional mismatched data type identifiers is based on the third data type being incompatible with performing the operation that calls for the reassigned second data type; and based on determining the additional mismatched data type identifiers, cause each value from the third subset of data entries to be reassigned to the second data type.
 37. The method of claim 30, wherein the data type identifier changing application is configured as an add-in application to an application selected from one or more of a database application, a spreadsheet application, or a data wrangling application.
 38. The method of claim 30, wherein causing each value from the first subset of data entries to be reassigned to the second data type includes: determining whether reassigning the first data type identifier to the second data type identifier for any of the first subset of data entries would cause invalid data in other entries from the dataset; and reassigning the first subset of data entries to the second data type is based on determining that reassigning the first data type identifier to the second data type identifier would not cause invalid data in other entries from the dataset.
 39. A non-transitory computer readable medium storing instructions thereon that, when executed by one or more processors, causes a computing device to: identify a dataset including a plurality of data entries, each data entry from the plurality of data entries having a data type identifier indicating a type of data for a value in the corresponding data entry; determine mismatched data type identifiers within the dataset based on a first subset of data entries from the dataset being associated with a first data type and a second subset of data entries from the dataset being associated with a second data type, wherein determining the mismatched data type identifiers is based on the first data type being incompatible with performing an operation that calls for the second data type; and based on determining the mismatched data type identifiers between the first subset of data entries and the second subset of data entries, cause each value from the first subset of data entries to be reassigned to the second data type.
 40. The non-transitory computer readable medium of claim 39, wherein the dataset includes a relational database of data including a table of data entries, the table of data entries being organized in a plurality of columns and a plurality of rows, wherein the plurality of data entries includes a selected column or row of data entries within the table of data entries, and wherein the first subset of data entries and the second subset of data entries are interspersed throughout the selected column or row of data entries, and wherein at least one data type identifier from the two or more data type identifiers include data entities selected from one or more of an address, a social security number, a phone number, or a zip code. 